android/mlc4j: fix FFI include (traceback -> backtrace) #3355
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Android mlc4j build fails because tvm-ffi renamed `traceback.cc` to `backtrace.cc`. Replace the stale include with <ffi/backtrace.cc>. This is the minimal change to restore build without touching other code. (Using a .cc file in headers is generally discouraged, but this keeps the current structure intact and unblocks builds.) - Change: #include <ffi/traceback.cc> -> #include <ffi/backtrace.cc> - Scope: android/mlc4j/src/cpp/tvm_runtime.h - Verified: local Android build succeeds
MasterJH5574
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Android mlc4j build fails because tvm-ffi renamed
traceback.cctobacktrace.cc. Replace the stale include with <ffi/backtrace.cc>.This is the minimal change to restore build without touching other code. (Using a .cc file in headers is generally discouraged, but this keeps the current structure intact and unblocks builds.)